Network identity
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Manual: Network Identities ↗
A network identity is a standard Reticulum identity that is used by one or more transport nodes to identify them as belonging to the same logical group of nodes (a logical network). It can be thought of as a cryptographic flag, similar to a charter that flies over a fleet of ships, signalling that it belongs to the same organization or community.cite-ref-1[1]
Contents
Current use
It is currently used in interface discovery where it provides authenticity and trust boundaries, making it possible to only auto-connect to networks you have some level of trust in, effectively creating "whitelisted" zones of trusted infrastructure.
Future use
It is the foundation for several planned features, such as distributed name resolution, distributed blackhole management, inter-network federation and publishing of network capabilities, services and information endpoints. Adopting network identities now prepares your infrastructure for these upcoming features.
Configuration
Specify the path of the identity file to use as the network identity in network_identity of the RNS configuration file.
To create a new identity file, use rnid (e.g. rnid --generate ~/.reticulum/storage/identities/my_network).
See also
References
Reticulum concepts
Announce • Blackhole • Buffer • Channel • Destination • Discovery • Identity • Instance • Interface • Interface Access Code (IFAC) • Link • Network identity • Node • Packet • Path • Propagation node • Resource • Stamp • Transport node